06. Non-user stories: What to include

ND036 C3 L3 04.2 What Are Non-User Stories-

ND036 C3 L3 04.3 What Are Non-User Stories-

What are non-user stories? Recap

Business and system-level requirements that are co-created by Product Manager and engineering are called as non-user stories or non-functional requirements. In some instances, both PM and engineering lead for the project to collaborate with stakeholders (internal and external) depending upon the type of requirements to understand the requirement fully to determine how to support it. An initial checklist to begin capturing these requirements:

  • Performance e.g Response time, latency, throughput
  • Scalability e.g Scale up, Scale down
  • Reliability and Disaster Recovery
  • Auditability requirements driven by regulations, legal and compliance
  • Accessibility
  • Support to run experiments and analytics tracking
  • Browser and device compatibility
  • Others include Security, Internationalization, etc

What are non-user stories?

For a minimum viable product that is being launched to a smaller audience and focused on iterating, the Product Manager need not focus on non-functional requirements to be captured, developed and tested to launch the feature.
SOLUTION: False

Next Concept